home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Night Owl - The Best of BBS
/
Night Owl The Best of BBS (NOP-BBS) (Night Owl Publisher) (1994).iso
/
022a
/
jm940310.lha
/
readme
< prev
Wrap
Text File
|
1994-03-08
|
21KB
|
618 lines
Those of you currently running a version of Jammail, please send me a message
with your current wish list and i'll see what I can do.
Please send me a message with any wishes about the new Jammail1. I am
doing a completely new GUI so any changes you'd like to the editor, now
is the time to tell me!
Changes - March 7, 1994
- little more tweeking with wplemsi.library.
- version string changed for the welcome banner.
Changes - March 6, 1994
- New JamMail1-preview program. Massive changes to most list-views,
and the scheduler screens have actually been done.
- Adding Ymodem as an additional available protocol. This is usefull
for systems that may have flow-control problems. It is positioned
between Zmodem and ZedZap. If someone is having flow control
problems, they should disable DirectZap and ZedZap. Ymodem will be
the highest priority EMSI protocol, so mail from other systems
supporting Ymodem will hopefully be more reliable. Zmodem/ZedZip should
still be left on as other systems will be using it.
The XprYmodem.library file is included if you don't have it. If you
are low on space or ram, simply disable the protocol and delete the
file. This protocol is simply a little extra that some systems may
find handy.
- The "Write Setup" menu option, lists the librarys that JamMail uses
or doesn't use, and it will tell you if your inbound or outbound
directory does not exist.
- New WPL.Library included in the archive. This one has no debugging
in it at all. Along with a clean compiled wplemsi.library, things
should be debugging free.
- Massive work on the JamMail1 gui and new JTPhone gui. Hopefully i'll
have a new JTPhone out soon.
Changes - February 26
- Added launch code for MEBBSNet BBS.
- Added configurable switch to make JamMail ignore possible error
codes from the BBS making JamMail hangup irrelevent of some error
happening.
- Fixed readconfig code, that wasn't allowing multiple BBS Launch
commands.
Changes - Feb 25
- AHHAHAHARGHRGHG I screwed up. The last two archives (the 25th, and
the 18th) likely still had all of the EMSI debugging turned on. So
if you were using the internal serial port and weren't running SUSHI
you'd have no prayor trying to get an EMSI session.
Changes - February 24
- Not much happening in the way of this JamMail. I'm trying to get
a bit going with the new Preview version. The Preview binary
in here is the same as the Feb 18th version.
- There has been some reported problems with the new JamScan56
binary on some machines, with it causing a GURU. IF this does
happen, go back to version 55 (the jamscan055.lha archive is
available on my system, and many others).
- I've done a *LOT* of work on the JamMail1-preview manual. this
one won't go out until JamMail1 itself does since the description
of the software, is relative to the new GUI version of the
software, and some options are in different locations.
- Possibly fixed UUCP/UUCP2 sessions to use any and all versions of
UUCICO, by adding the -Getty switch on outbound calls as well. As
far as I know, they all worked fine for inbound calls, but should
work for outbound as well now.
Changes - February 18
- Gotta love it when I forget to update the .readme :-)
- tweeks and changes in various areas of the system. I can't
remember what all I changed.
- JamScan now allows upto 200 config lines. Previously it was
50 and I just hit that myself :-)
- JamTool has been updated to use a much faster method to do the
EMSI AKA lookups. A new JamTool archive has been sent out
as well.
- All of the AKA/Remote Changes menu options are valid for outbound EMSI
sessions as well (ie, directories, system names), and EMSI itself
can now be disabled (previously it could not be disabled).
- you can now set an option to abort on a CTRL-C in one of the
modem windows. You need to press ctrl-c twice for it to work
however. I'm going to see if I can do anything about this.
Changes - February 6
- Missing Label Error for Fax sessions fixed (DoDial4.4)
Changes - Feburary 2 - 5
- Lots of cleaning up of wplemsi.library.
- EMSI_REQ banner for receiving calls is now hidden to human callers.
(<cr> sent with no linefeed).
- other tweeks with the jammail.wpl file.
- two digit "hex" Product ID is sent in EMSI banner, although since
WPL is 07, it didn't make much difference :-)
Changes - February 1
- Fixed up wplemsi.library. I wasn't verifying the EMSI CRC's because
of a UBYTE problem that I had fixed, but hadn't enabled the CRC
checking again.
Changes - January 31
- There's been a few strange hangups during XprZedZap file transfers.
There is a possibility this is related to Yves's version of the
library. If this problem continues, I am going back to Russ's
version of the library that does not support DirectZap. You will
be able to pickup Yves' library seperately if you wish, but I will
not be including the library capable of DirectZap unless the bug
is found.
Changes - January 30
- *SHIT* right after making up the archive, I found a bug I introduced
yesterday in the wplemsi.library. The host.sitename was not being
sent. No major problem, people just didn't know what the system name
was that was calling them :-)
Changes - January 28
- Cleaning up for an update to the 1210 and 1216 and archives.
- changed name of xpremsi.library to wplemsi.library (since no other
xpr host can use the library right now).
- removed my getline2 function (for string editing) since it was
causing problems, and the new GUI version of JamMail won't be using
any of this stuff anyways.
For people that need to edit some of the really long strings like
possibly your EMSI AKA string, use a regular text editor to edit
the s:Jammail.cfg file, but be carefull not to change anything
else. When you run JamMail to read in that file (and to generate
the mailer), make sure that string was read in correctly).
Changes - January 24
- Fixing up Collision detection with replycall and forward call stuff.
Changes - January 23 - 18
- Various fixing up relating to EMSI
- Inbound EMSI was "finished" sometime in here.
Changes - January 17
- Fixed few minor bugs relating to not having any AKA's or MenuFiles
configured (it was defaulting at having something).
- Finished LogWindow menu.
Changes - January 16
- Window editing displays are fixed up a bit (displays size and upper
left corner instead of raw:x/y/x1/y2 format).
- asynchronously launching bbs's :-)
- Completely re-vamped input routine. Insertion and cursor keys (left/
right) now work.
Changes - January 15
- The version number is now automatically being updated (i'm lazy:-)
- Added NoDrag/NoSize and BackDrop options to LogWindows menu. *ALL*
windows will have these options (except xpr transfer windows will
not have backdrop option);
- Now generating S:Setup batch file. Logfile and LogWindow are now
configurable and written in this file. The LDPhoneLog is also
configurable and written in the setup script.
Changes - January 14
- Added Modem Banging config. 3 choices. Soft, Medium and Hard.
This selects which string will be sent to the modem after every session
to get control of the modem back (ie, until an OK response is received).
NullModem.Device does not support the Hard banging type.
The Soft is basically an AT, the Medium is an ATZ and the Hard is an AT&F.
If you previously had the Medium or Hard in your Init string, you don't
need it any long if you use it here.
- All protocol selection code is generated only if needed. If you don't
want ZedZap used, no inbound or outbound zedzap code is written to
the .wpl file.
- Init and Attention modem strings lengthened to 60 characters.
Changes - January 13
- Added DirectZap support for outbound EMSI sessions. (I think !? :-)
- Cleaning up inbound Fidonet sessions now. WaZoo and EMSI protocol
selection is now done the same way as the way i'm doing it for outbound
protocols. Now all we need, is Inbound EMSI support.
Changes - January 12th, 94
- more internal cleaning
Changes - January 11th
- My USHayes V.FC 28.8k modem arrived. I'm going to change the (TIME)
response type to a simple (LOG) response, so anything that has this
response type will simply be logged. Nothing else special is done
with anything that matches. Also, the response type (LOG) will not
be put on the end of the line (like RING and others is done).
- All outbound Fidonet session code re-done. It is now easy to add
new protocols to WaZoo or EMSI sessions.
- Protocols available are now configurable in Fidonet -> Other menu.
- Re-write of alot of the outbound dialing sequence. Collision detection
is now much better (theoretically!).
- Additional internal ModemInit added to mailer. Cleans up alot of
possible junk that could happen before main INIT was done after a
dial/session.
Changes - January 10th
- Still cleaning internals & sources
Changes - January 9th
- Massive cleanup of internal JamMail code.
- You can now only select Handshaking methods for your Aka's that are
turned on by default.
Changes - January 8th
- Added UUCP2 session type. You may want to have two different sets
of UUCICO options, one for regular systems, and one for systems that
can handle larger block sizes and faster sessions.
JTPhone will be updated to handle this as well.
- I think inbound FAX reception has been fixed. Thanks to Todd Vierling
for the code.
Changes - January 6th
- The AddModem fuction should actuall add the correct defaults for the
modem you select.
- Actually fixed the defaults for Nullmodem.device lines.
- Included the CNet BBS launch string as default #3. Since it is only
a single command line, the command line is actually placed in the
launch string so you can see it (the DLG and VBBS launch commands are
more than one line, so are just generated in your mailer).
Changes - January 5th
- Oops, I haven't been making my entries!
- Full outbound EMSI is now being done (actually, it was done before my
Xmas vacation, but I didn't mention it here :-)
- Scheduler timeouts now have a maximum of 9999 seconds instead of 255.
- Init timeout value is now configurable for each line (wasn't configurable
at all previously).
- Pre-fido bug reported in wpl-programmer fixed.
- inbound and outbound directory prompts actually add '/' character if
not already there.
--------
Happy New year guys!
Changes - December 15
- Back to EMSI work. Now actually attempting to do WPL variable handling
from inside XprEMSI.library.
- latest Wpl.Library included in archive now. - Fixes RexxMsg bug.
Changes - December 8
- Completely cleaned random "OK" messages popping up in log messages that
come back from modems that take a long time to init (ie, slow 2400 with
an AT&F in the init string).
Changes - December 5
- Still playing with EMSI (not included in this archive)
- New security option added to JamTool/JamMail. This makes sure people
aren't using the nice escape sequences possible in the execute commands
in either the main login menu, or the freq server name input routine.
Changes - December 3
- Due to the Mad hacker - i've cleaned up a few input routines that
could have been used to do nasty things.
Changes - December 1
- Fixed timeout in ModemInit routine that was causing "OK" results
to show up in the main log window with extreamly slow modems (slow
at resetting if you did an ATZ as your init/atten string).
- Setting the current modem to 300bps before dialing NRC systems for
better compatibility with different modems attempting to do the
connection.
Changes - November 22-25
- Working on outbound EMSI support. This stuff will not be included in
the current archive, but this is to let you know what i'm working
on. Inbound EMSI will be added after outbound is done.
Changes - November 21
- problem with "-ListConfig" command was causing a guru after
startup of JamMail. The command has been removed since it was only
being used for debugging purposes anyways.
Changes - November 19
- Now including JamScan and JamTool in the JamMail archive along
with their respective documentation files.
Changes - November 18
- Lots of work done on the Documentation. Completed the FidoNet
configs area (updated to the new menu set), and added the Login
Menu section.
- archive is now named in the "JamMailDDMM.Lha" style, with the
day and month.
Changes - November 17
- Re-structuring menu system - Fidonet options are cleaned up, the
documentation will be a little wrong during this time. The Privacy
modes are now a single option in the "Login Menu" that selects each
of the options in order. Cleaning up the code that uses these
settings as well.
- The inbound and outbound directory selections were moved to the
Fidonet configs menu.
- privacy variables removed, more cleaning up.
Changes - November 16
- Call script included. You can set the Execute bit on this script
or have an alias that executes it. This command will take a single
parameter (an address, or portion of a FTN address) and it will
add that system to the scheduler dial list.
- Due to this change with the scheduler, when call collisions occur,
calls are forwarded back to the scheduler in hopes that the call
being attempted can be sent to another line (if this is a multi-line
system).
- Finally updated TODO: list. Most of it had been done!
Changes - November 15
- Scheduler slave (message port "JAMMAIL") now accepts call commands.
After it scans for systems in Xferq (and UUSPOOL: if configured to
do so), it will check to see if a call command has been sent to it.
If a call has been received, that system is added to the top of the
ToDial list, and it will be dialed first. Only one call command
per scan will be added. It is recommended that you use an alias
like:
Alias Call run <nil: >nil: rx "Address 'JAMMAIL' 'Call []'"
to do manual dials.
If you wish the call to be done immediately (assuming it is in a
waitloop), send a Ctrl-F (Timeout) to the slave right after you
send the Dial. (You could have the CALL Alias execute a script
that does both).
Changes - November 10
- The scheduler accounting system now does not operate on "TERM" type
dials, so it does not dial less often to these systems if they are
busy.
- One Note: currently, UUCP dials (systems looked up in the UUSPOOL:
directory, don't use this system either). Anything that uses Xferq
(other than TERM types) does.
Changes - November 7
- Fixed a couple windows up. The introduction of Public Screens wasn't
completely finished :-)
Changes - November 4
- Bug fix - the system wasn't allowing the situation where the user
didn't have any AKA's configured. It defaulted to having one,
which caused problems with the written script.
Changes - October 31
- Working with Scheduler/JamTool. Added everything to JamMail.wpl
scripts for the new sheduler accounting system (dialing less often
if the system is down, busy etc..).
- JamTool Env: variables are now in a Sub-directory, clearing your Env:
directory a bit (ToDial variables).
Changes - October 25
- Added ability to run JamMail on a Public Screen. You still need to
edit the s:setup and s:setup.cli scripts to move the "setup" and
the main Logwindow to this screen as well. I will likely generate
these two scripts inside JamMail in a future version.
- Due to the above fact, and that I wanted to run a 1 bitplane screen,
there is now an option to turn off the colors that I was using in
past versions. Likely i'll enhance this in the future to use more
colors when its in color mode.
- Both of these changes are in the Main Logging options menu for lack
of a better location.
- Set internal window defaults to be more usable by "regular" users.
- Using Custom input routine for getting Modem Stats window specs.
Changes - October 16
- Minor tweeks, Optimizer option turned on.
Changes - October 5
- fixed bug in ReadAnswer() function (reads part of the config file),
where it wasn't changing the variable that was the number of files
you had configured for the login menu.
Changes - September 23 - 29
- minor tweeks and twitches. Nothing major
- just toying around. Playing a bit with various things.
Changes - September 22
- Fixed up scheduler. New Option: Ctrl-D in scheduler window starts
your wait delay over again. Wait delay is now shown in window.
After each session (inbound or outbound) this wait is started over
again, and the scheduler loop is reset. This means that if you had
6 sites to dial, and you connected to the 3rd one, the loop would
start again, do a scan, and you'd have 5 sites to dial. This also
stops the collision where a site calls in, and he had been further
down in your dial list, and you dial this person, even though you
don't have mail for them anymore.
- suggested timeout values are 60 between scans and 10 between dials.
Changes - September 21
- installed nullmodem.device so I now have a second line (sorta) to play
with. allows me to login to my own system without using both phone
lines.
- problems with scheduler that had been screwed up a bit since I've only
been running one line for the last month or so.
Changes - September 20
- problem with new wpl.library - changed call command to wait for reply.
- will fix this for multi-line scheduler later on. Single line users
won't care.
Changes - September 19
- new version of wpl.library installed - put signal slave commands back
into the system.
- created new jammail.test file. Most binaries are put in the bin/
directory. The jammail.wpl and jammail.cfg files are now located in
S: as are the setup and setup.cli scripts.
Changes - September 16
- still working on documentation.
- starting on documentation of File request support - its going to be
a real pain!
Changes - September 12
- Starting on real documentation.
Changes - September 11
- fixed a bug in the Menu Files menu where you enter the command name.
it was allowing filenames longer than the array size. This is now
extended to 20 characters.
- Finishing up JamToolPhoneBook. - Added range delete mode.
Changes - September 8-10
- Massive work on Jamtool
- New Lookup routines with JamTool
- JamTool Phonebook Editor introduced.
Changes - September 5
- NRC Dialing fully setup and working.
- Finished Config file.
Changes - September 4
- Fixed NRC calling. It is now a Jamtool.phone entry. NRC options
in the menu will be stripped down to only the necessities.
It is recommended that you list the flags for your NRC entry as
being 300, and then set yourself up a dialing string based on a
Flag of #?300#?. This would then be the string to force your
modem down to 300bps. I am using AT&n25&k0dt with my ZyXEL.
This turns off all compression, and selects BELL 103.
- Found problem with 300bps connections. Response orders changed in
internal modem definitions. The "CONNECT" response string must
be listed after all other connect type responses that you want
to support. "CONNECT " (with trailing space) is used for the FIND
type, and a "CONNECT FAX" or some such thing is good. They must
be before "CONNECT" as it will match the others.
Changes - September 3
- Due to having to work on Gordon a bit, i've been a tad busy, but
i'm back at it!
- Config file is now readable!
******************************************************
- Changes from March to August 93 Deleted -
******************************************************
Note: You *MUST* be running SUSHI or have a terminal connected to your internal
serial port to use the current debugging versions of wpl.library and xferq.library.
Unless otherwise stated, you will be running debug versions of the librarys if you
got them with this archive.
-----------------------------------------------------------------------
TODO:
- Documentation!
- Long distance calling window - "DIRECT" mail during ZMH type of thing
but specific to certain days, and not every ZMH.
- open logproc logs in JamMail.Wpl. Possibly even an additional "pop-up"
log window for each line.
- built in "Point" configuration - main menu option, reconfigures whole
system with "point" type values. Tells user which settings to manually
change.
- Audio inbound/outbound file announcement option (configurable messages).
- Seperate "session" log. Only logs address, and session times (connect,
disconnect and session time).
- ability to launch .wpl scripts from commands input on login menu.
- Auto-window location generator (calculates "good looking" locations for
log/session/scheduler windows).
---- Way Way Future TODO list
- Outbound Fax dialing - requires me to have GPFax or some other piece of
fax software (looking at ElCheapoFax).